It’s a bug I also got with 2024.1 and still experiencing. When I start to render a queue the first render is terribly/painfully slow. Like just 30 samples a minute while the scene’s performance is more like 600 samples a minute.
If I abort the render and start the queue again it’s all fine but the aborted render is of course lost from queue.
Communication done earlier via email/support etc., besides fixing this bug it would also be nice if an aborted render stays inside the queue. That makes more sense since it’s not finished. Aborting ain’t the same as delete the item from queue.
I need to check the actual scene again and I’m about to move to another place so currently in the stressful process of packing all PC-related things.
It’s an odd thing though, a lot of times also the real-time render view slows down to a few samples per second. If I save the scene and open the same again it it’s running at normal pace again.
Bit hard to figure out the cause but with 2024.2 some changes in the scene seem also to freeze the GPU more than earlier. For example, changing a color, or changing a roughness value of a texture. It takes like 5-10 second or so to be able to move the cam around again and the image gets updated.
When I’m settled, I’ll try to to some extra reporting, are some other things I noticed as well but with the upcoming move all is a bit slow here. #notmyhobby
I, too, have had the same experience of making a material change, or even a change to an animation parameter that causes Keyshot to hang for your stated 5-10 seconds before I can move the camera again (GPU mode). I have an animation due for work soon and when I am back in it, I will report what I am experiencing specifically as well.
